[POWERPC][XEN] make sure Dom0.VCPU0 is pinned to the booting CPU
authorJimi Xenidis <jimix@watson.ibm.com>
Fri, 1 Sep 2006 16:37:29 +0000 (12:37 -0400)
committerJimi Xenidis <jimix@watson.ibm.com>
Fri, 1 Sep 2006 16:37:29 +0000 (12:37 -0400)
Signed-off-by: Jimi Xenidis <jimix@watson.ibm.com>
Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
xen/arch/powerpc/setup.c

index 59c17f24921d3587fb74fec83424e9dbc83edd9e..47ca0c3fcb6b8dbc5297d5a356f3af9723cfccbf 100644 (file)
@@ -344,6 +344,10 @@ static void __init __start_xen(multiboot_info_t *mbi)
     if (NULL == alloc_vcpu(dom0, 0, 0))
         panic("Error creating domain 0 vcpu 0\n");
 
+    /* The Interrupt Controller will route everything to CPU 0 so we
+     * need to make sure Dom0's vVCPU 0 is pinned to the CPU */
+    dom0->vcpu[0]->cpu_affinity = cpumask_of_cpu(0);
+
     set_bit(_DOMF_privileged, &dom0->domain_flags);
     /* post-create hooks sets security label */
     acm_post_domain0_create(dom0->domain_id);